Shareware Grab Bag/Shareware Grab Bag.iso/001/autoprc1.arc/AUTOPRCM.DOC

Text File | 1986-09-21 | 11.1 KB | 226 lines

.op
.po 0
                               AUTOPRCM.COM

                       Version 2.0 - September 1986

        Copyright (C) 1986 - John L. O'Boyle - All Rights Reserved

     A  routine  to  generate DOWNLOAD scripts (.CMD  files)  for  ProComm*
version 2.4 and greater.

     This   program was developed after seeing a version originally written
by  Keith Peterson.   The one I saw had been modified for use with  PIBTERM
and RBBS systems only.   While RBBS is nice,  it's not the ONLY Host System
in  the world!   I've included File Transfer Protocol and Host options  for
several popular systems.  If the routine is well-received, I'll continue to
update it as hosts systems (or ProComm) change.

FORWARD:

     One  of the nicest features of ProComm (this authors opinion only)  is
it's CMD processor!   CMD files contain, among other things, the keystrokes
you  would normally have to enter manually for a given task.   The  ProComm
documentation covers this subject much more completely and  elegantly,  but
the  "biggies" are the WAITFOR  statement and the TRANSMIT statement.   The
WAITFOR statement says.."wait until these characters are received from  the
host".   The  TRANSMIT statement says.."send these characters to the host."
You can see where, with a little experimentation, you could build a file to
do  just about anything you wanted,  provided you KNEW what to expect  from
the host.

     CMD  files can be built with any editor or word-processor.   Many  BBS
systems  offer ProComm CMD file examples that will completely automate  the
logon sequence for their particular system.   These need only be downloaded
and modified for your individual use,  ie;  change the sample-name to  YOUR
name, etc.

     CMD  files can be executed directly from the DOS command line when you
execute ProComm.   (Again,  please refer to the documentation that Tom  and
Bruce  provide.) Using this feature,  it's possible to execute ONE DOS com-
mand  which will invoke ProComm,  execute a CMD file which will logon to  a
given host, go directly to the <F>iles section, download a list of the most
recent file additions,  logoff the host system,  disconnect the phone line,
print the downloaded list,  and exit ProComm.   (I do it all the time...and
by using the TEF program, I do it in the middle of the night when the rates
are lower!)

     If  you haven't yet discovered the CMD feature of ProComm,  maybe  AU-
TOPRCM will help you get started!

OPERATIONAL CONSIDERATIONS:

     This  program may be run from WITHIN ProComm,  to produce an immediate
".CMD" file for file transfers.   I've substituted it's name for the Editor
option   in   my PROCOMM.PRM.   While on-line to a system,  the  ALT-A  key
sequence initiates the program.   Of course it can be run stand-alone  any-
time!

     I  suggest that users run the program a few times to  become  familiar
with  the  files  produced.   (AUTOPRCM produces ONE output file  per  run,
called  "DOWNLOAD.CMD")  The .CMD will be activated  at  different  prompts
depending on the host system.   Once you know what the FIRST command in the
file  does,  you'll  only have to get to the requisite prompt on  the  host
system and trigger the .CMD file via ProComms' ALT-F5 key sequence.

     It's recommended that .CMD files,  created via AUTOPRCM, NOT be run in
an  unattended mode!   A misspelling of a file name and/or changes in  host
prompts may cause the .CMD to WAIT on an unexpected prompt.  If a .CMD file
hangs, the ESC key will return you to manual control.

     It's also recommended that you have a copy of the host download direc-
tory handy when you create your .CMD file,  or at least good clear notes if
you're running the program dynamically.   Scan the host directories for the
files you want,  make a list of those files,  and USE the list when you are
running AUTOPRCM.


MINIMAL NOTES ON SUPPORTED HOSTS:

RBBS - Currently only provides Xmodem protocol.  (ASCII was not included in
AUTOPRCM  since most useful files are not stored in that form.) Since  RBBS
allows the download command,  the file name,  and the protocol option to be
specified via a single string,  (ie;  "D;ANYFILE.BAS;X") the "DOWNLOAD.CMD"
file begins with this command.

IBBS - The above notes from RBBS apply here also.

Source  IBMSIG  - The  DOWNLOAD.CMD begins from a MAIN SYSTEM  PROMPT  ">",
external to the IBMSIG!

PC-Board  - The  transfer protocol you use from a PC-Board system  is  con-
tained in your PC-Board user profile.   Be certain that the one you  choose
for  AUTOPRCM matches that used in the PC-Board system you  contact.   This
.CMD starts from the "Enter File Name" prompt.

EXEC-PC - Download via Kermit,  Xmodem and Ymodem.  Expects to find prompts
generated by the e<X>pert Mode.

FIDO  - Prompts  and  protocols for FIDO systems are in a  state  of  flux.
AUTOPRCM supports Xmodem,  Kermit,  Telink,  and Modem7.   This .CMD starts
from the "Enter File Name" prompt.

PC-HOST    - These systems do not use filenames for security  reasons.   Files
are selected via number from a directory list.   AUTOPRCM will BEGIN with a
directory change command,  and continue from there.   For Kermit and Ymodem
Batch, only the Dir # and File # must be specified.  For Xmodem amd Ymodem,
an additional file name is required.

    CRC-16 verification will be always be utilized where available.

CAVEAT:

The  various  host  system prompts that are produced in  AUTOPRCM  for  the
WAITFOR  command were accurate as of this release!   I have NO control over
these  prompts  if they have been changed by a given Sysop for his  or  her
particular software.   Should you discover that a system prompt has changed
(and  it MUST be for the generic system,  ie;  ALL RBBS systems),  I'll  be
happy to modify the code if you let me know what's changed.  Notes, sugges-
tions,  or  comments on AUTOPRCM can be left on the PConnecticut BBS  (203)
521-1991  (1200/2400 only).   The LATEST version of AUTOPRCM.COM can ALWAYS
be   found  on that system,   the Datastorm Technologies System,   and  the
IBMSIG on  The Source.

    To change AUTOPRCM default values, see the section on Auto-patch.

BATCH MODE OPERATION:
     AUTOPRCM  batch-mode was the result of a (what I first thought was  an
unusual)  user request.   I initially didn't see the advantage to be gained
in using .BAT files to do ALL the work.   I now LIKE the idea of being able
to use a "list of new files" for example from RBBS, and just plug that file
into the AUTOPRCM.DAT file.   Saves having to re-key (and possible mis-key)
the file names!

Basically...
     AUTOPRCM LOOKS for a file named "AUTOPRCM.DAT".   If it finds  it,  it
operates  in  "batch" or "semi-automatic" (discussed later) mode.   In  the
absence of AUTOPRCM.DAT, the program operates as originally designed.

     The particulars are...  You ALWAYS get Auto-logoff.  If the FIRST line
of AUTOMENU.DAT is NOT a PATHSPEC, the default is used.  The SECOND line of
AUTOPRCM.DAT  (or the first if the path is missing) MUST be a system  name,
Source,  CServe, TComm, etc.  It's not case-sensitive, and only scans  four
characters, so you don't even have to spell it all the way out.

     The third line (or second..see above) is the Transfer  Protocol.  Same
thing  here.  Only scans four characters and either upper or lower case  is
fine.   Subsequent  lines are file names.   AUTOPRCM  extracts to the FIRST
blank,  so  it's  possible  to leave the descriptions in the  line  if  you
prefer.   (I  did that with the RBBS listing.)  That's about  it.   There's
almost NO error checking.  If a filespec length is bad, it STAYS that way.

SEMI-AUTOMATIC MODE:
     Turns  out  that after the coding for the batch-mode was  complete,  I
ended up with a semi-automatic mode without doing any further work.

     If  AUTOPRCM.DAT exists,  AUTOPRCM will look at  it!   Straight  ASCII
file.   Nothing special.   The FIRST thing AUTOPRCM expects to see is a new
directory specification.   As in..."G:\THISISIT\".   Turns out though, that
if it's NOT there (as the first record of the file),  AUTOPRCM will use the
hard-coded  directory  and NOT give you an opportunity to change it on  the
fly!   The  SECOND line of AUTOPRCM.DAT (or the FIRST,  if the path  wasn't
specified) MUST be a host system name.   Again, it can be mispelled to some
degree,  since  AUTOPRCM only checks three or four significant  characters.
Any further lines will cause AUTOPRCM to operate in batch-mode.

     Thereafter,  AUTOPRCM operates in manual mode, but you've saved having
to enter the PATH and/or the host system name.


AUTO-PATCH:
     Some  defaults in AUTOPRCM can be changed via the auto-patch  feature.
These changes will remain in effect until a subsequent auto-patch operation
is performed.

     With NO AUTOPRCM.DAT file around, execute AUTOPRCM.  WHILE the logo is
painting, hit the F1 key.  You'll see another selection which allows you to
change the default path,   optionally skip the path prompt in future execu-
tions,  and  decide  if AUTOPRCM.DAT should be  deleted  during  batch-mode
operation.   AUTOPRCM  will modify itself and exit.   If you don't like the
way it works, do it over again!  The only restriction is that AUTOPRCM MUST
be in the current directory.

That's it!

I'd  like  to  take a minute here to thank two  Mikes,  Todd  and  Callahan
respectively,  (of The Source IBMSIG) for  their considerable input to, and
relentless  testing of,  this program.   They provided both the support and
motivation necessary for me to finish it co-incidental with the release  of
ProComm 2.4.

AUTOPRCM  is distributed on the SHAREWARE concept and is NOT Public  Domain
Code.
          This program  is  copyright  (C)  1986,  by John L.  O'Boyle. All
rights reserved.   Non-registered users are granted  a limited  license  to
use this  product on a trial  basis,  and to copy the program for trial use
by others subject to the following limitations:

The program is distributed in unmodified form, complete with documentation.

No fee, charge or  other consideration  is requested or accepted.

If  you intend to  use  AUTOPRCM on a  regular  basis,  please register and
show your support for the author.    Commercial, business  or  governmental
use  by  non-registered users is prohibited.

     Registrations, and the associated $5.00 fee should be mailed to:

           John L .O'Boyle PO Box 10596 West Hartford, CT 06110

Since this code is useless without PROCOMM,  please be certain that  you've
also  supported  THAT  product via registration!   If it gets to  a  choice
between me and them, please send THEM your money first!

     The usual disclaimer applies to AUTOPRCM.   NO WARRANTIES EXPRESSED OR
IMPLIED!


* ProComm is a trademark of Datastorm Technologies, Inc.


V2.4 Copyright 1985, 1986 Datastorm Technologies, Bruce Barkelew & Tom Smith

      Datastorm Technologies, Inc.   P.O. Box 1471 Columbia, MO 65205

  ProComm support BBS [phone] 23 hrs per day, 4:00 - 3:00 am CST.